bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Mon, 9 Sep 2024 12:56:19 +0000 (14:56 +0200)
committerGianfranco Costamagna <locutusofborg@debian.org>
Mon, 9 Sep 2024 12:56:19 +0000 (14:56 +0200)
commit22befbc932a019be9758f51be05468ef82323cee
treea38a3c4fefb04758f597f67de6b105943b68366d
parent965f759ceb38179c7792c3323258ffc21a60167e
bootstrap-fix-include-next

When doing a bootstrap, we use a newly built clang.
When this one is used, if already installed on the system,
we have clang header in two places:
llvm-toolchain-7-7/build-llvm/lib/clang/7.0.0/include/inttypes.h
and
/usr/include/clang/7.0.0/include/inttypes.h

Because clang expects only one of his headers to be available, it uses
include_next to get the glibc (libc6-dev package) header.

However, in the previous example, because we have inttypes.h twice in the
include search path, clang's header will call itself without any effect.
Therefore, it will do include_next until the define from the libc is existing (ex: _INTTYPES_H)

Gbp-Pq: Name bootstrap-fix-include-next.diff
clang/lib/Headers/inttypes.h
clang/lib/Headers/limits.h